home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
clipper
/
nftroff.zip
/
16.tr
< prev
next >
Wrap
Text File
|
1991-11-21
|
6KB
|
282 lines
.de }n
.bp
.sp .5i
..
.wh -.8i }n
.sp .5i
.po -.4i
.ll 7.5i
.ps 9
.vs 9
.in 0i
.sp 2
.ne 20
.ps +3
.vs +3
Recompiling the source code
.br
.ps -3
.vs -3
.sp 2
.sp
.in 0.32i
\fBThe Nanforum Toolkit Master Makefile
.sp
This makefile will allow you to use RMAKE, provided with every
Clipper 5\.0 package, to maintain your own copy of the Nanforum
Toolkit\. It is also a good example of how to use RMAKE on a
large project\. This is the exact copy used by the Nanforum Toolkit
librarian\.
.sp
To use it, you must first understand what it does, and what your
limitations are\. A discussion of MAKE utlities is beyond the scope
of this comment; read the Clipper documentation, or the Norton Guide
file, for more information on RMAKE\.
.sp
\fB*** Compilers and Assemblers you need
.sp
Note that currently, Nanforum Toolkit sources are written in
Assembly language, Clipper, and C\. Within the realm of assembly
language, our contributors have submitted code that is designed
for Borland\'s Turbo Assembler (TASM) and Microsoft\'s Macro Assembler
(MASM)\. So, right now, in order to do a perfect re-build of the
Nanforum Toolkit, you must have these tools:
.sp
.in 0.72i
.br
Microsoft C (v5\.1 or later)
.br
Microsoft Macro Assembler (v 5\.1 or later)
.br
Borland Turbo Assembler
.br
Nantucket Clipper v5\.0 or later
.sp
.in 0.32i
If you know much about assembly language, you can convert MASM
sources to TASM and vice versa, but that is up to you\.
.sp
\fB*** Library Utility
.sp
In addition, you must have a library utility\. Microsoft supplies
LIB\.EXE with its Compiler products, for example\. LIB will work
fine with this makefile\. Note that we assume a command line syntax
for library utilities that works like this:
.sp
.in 0.72i
lib <libname> -+ objname
.sp
.in 0.32i
.ta 4.4i
Note the "-+" directive, indicating "replace module\." If your
.br
.ta
library utility does not support this syntax on the command line,
then you will have to edit the relevant lines in the makefile\.
.sp
\fB*** Assumptions about your environment
.sp
NFMAKE\.RMK makes just a few assumptions about your environment:
.sp
.in 1.2i
.ta 1.76i
Assumption What to change if we\'re wrong
.br
.ta
.ta 1.76i
---------- -----------------------------
.br
.ta
.sp
.in 0.32i
.ta 2.64i
Relevant environment Either edit the makefile to
.br
.ta
.ta 2.64i
variables for each compiler/ set the envars, or setup your
.br
.ta
.ta 2.64i
assembler are already autoexec\.bat to set them on bootup\.
.br
.ta
.ta 2.64i
set (i\.e\., LIB=, INCLUDE=) See your compiler doc\.
.br
.ta
.sp
.ta 2.64i
Microsoft C is being Look for the \.C source inference
.br
.ta
.ta 2.64i
used rule below, and change it to your
.br
.ta
.in 2.96i
compiler, making sure your switches
are correct\. Note that some source
may not compile without MSC, so edits
may be required\. Try to use MSC\.
.sp
.in 0.32i
.ta 2.64i
Microsoft Assembler Look for all occurences of MASM in
.br
.ta
.ta 2.64i
executable is called this makefile and change them to
.br
.ta
.ta 2.64i
MASM\.EXE whatever *you* call MASM\.
.br
.ta
.sp
.ta 2.64i
Clipper compiler executable Look for all occurences of "Clipper" in
.br
.ta
.ta 2.64i
is called CLIPPER\.EXE this makefile and change them to
.br
.ta
.in 2.96i
whatever *you* call Clipper\.
.sp
.in 0.32i
.ta 2.64i
Microsoft C executable is Look for all occurences of "CL" in this
.br
.ta
.ta 2.64i
called CL\.EXE makefile and change them to whatever
.br
.ta
.in 2.96i
*you* call CL\.
.sp
.sp
.in 0.32i
\fB*** Customizing the Makefile
.sp
We have tried not to assume anything about your environment except
what is described above\. To achieve that flexibility, you must
check and set some macros that can be found just below this
documentation\. They are:
.sp
.in 0.72i
.ta 0.8i
l Path to the resulting library (i\.e\., \\nanfor\\lib)
.br
.ta
.ta 0.8i
o Path to where \.obj files should be put
.br
.ta
.ta 0.8i
s Path to where the source code is found
.br
.ta
.in 0.64i
.ta 0.88i
c5 Path to Clipper 5\.0 compiler \.EXE
.br
.ta
.ta 0.88i
ma Path to Microsoft Macro Assembler \.EXE
.br
.ta
.ta 0.88i
ta Path to Turbo Assembler \.EXE
.br
.ta
.ta 0.88i
mc Path to Microsoft C 5\.1
.br
.ta
.ta 0.88i
ml Path and name of library utility (i\.e\., \\bin\\lib)
.br
.ta
.sp
.in 0.4i
Note that directory paths should *not* end in a backslash\.
If you like to keep your \.obj and source files in the same
directory, simply point the paths to the same place\.
.sp
\fB*** What happens when you don\'t have a compiler
.sp
If RMAKE can\'t find the compiler in the directory you specified,
then the relevant files designed for that compiler will not be
built, and the resultant objs won\'t be replaced in your library\.
You will get an error message\.
.sp
\fB*** Suggestions for setting up a "rebuilding environment"
.sp
Should you want to rebuild, the following is suggested:
.sp
First, make sure you keep an unmodified NANFOR\.LIB, downloaded
from the forum, in a safe place\. Do not modify it\.
.sp
Next, create a directory structure like this
.sp
\\nanfor
.in 0.72i
\\obj
\\src
.sp
.in 0.4i
Put this makefile in \\nanfor, and all source code into
\\nanfor\\src\.
.sp
Customize the makefile in \\nanfor for your environment\.
The default macros below assume you\'re using this arrangement\.
.sp
Type RMAKE NFMAKE\.RMK\. The \.obj files should be left in
\\nanfor\\obj, and the new NANFOR\.LIB should be in \\nanfor\.
.sp
Note that as new releases of the library come out, you may have
a lot of work incorporating additions and modifications\. So,
plan your rebuilding efforts carefully\.
.sp
\fB*** Problems, bugs, support
.sp
Support for this makefile can be found on CompuServe, in the
Nantucket Forum (NANFORUM)\. Leave messages in section 5 ("User
Lib")\. Updates and patches will be posted in Library 7\.
.in 0i
.sp
.in 1.5i
.ti -1.5i
.ta 1.5i
.ft B
See Also:
.ft R
Recompiling the Norton Guide
.ta
.in 0i
.sp 2
.ne 20
.ps +3
.vs +3
Recompiling the Norton Guide
.br
.ps -3
.vs -3
.sp 2
.sp
.sp
.in 0.32i
*** instructions on how to rebuild the NG go here ***
.in 0i
.sp
.in 1.5i
.ti -1.5i
.ta 1.5i
.ft B
See Also:
.ft R
Recompiling the source code